Daidalos Integration Framework TridentCom 2007

Daidalos Framework for Successful Testbed Integration Tridentcom 2007 Copyright 2007 Daidalos

Daidalos Framework for successful Testbed Integration

Frances Cleary GrantMiguel Ponce de Leon

TSSG – Waterford Institute of TechnologyIreland


Daidalos WP5

Daidalos (49 partners), integration was an immense task co-ordinated and implemented by WP5.

• Steps leading to Integration• Integration Tasks

Defining Integration Processes and ModelsDefining conformance test SpecificationsTest Site Planning,Deployment and IntegrationTest planning/scheduling/status report documentationTest case execution, fault detection, result reporting.

WP1

WP2

WP3

WP4

WP5

WP1

WP2

WP3

WP4

WP5

Phase 1Phase 2

1 2 3 4 5Duration/Year

R&D – First PhaseR&D – Second PhaseDemonstrator 1Demonstrator 2


Nidaros Scenario

PervasiveService Platform

PervasiveServiceManagement

Location &Network Information

Services

SecurityServices

Personalization

ContextManag.

Personalization

Identity, ChargingAAA. & PersonalMobility Services

user servicecontext

User Service Requestsand Advertisements

USRA P

Federation/SLA

Multimedia CallControl Signaling & Session Mobility Services

QoS BrokerServices

Federation/SLA

USC

LNIMCCS

Rules& Commands

Service &ResourceDiscoveryServices

SRDICAPM

Security &Privacy Manag.

Federation/SLA

SecurityConfig.

SC

Event Manag.

Federation/SLA

SEC

NetworkMonitoringInerface

QoSB

Federation/SLA

RulesManag.

RC

NM

SERVICE

PE

RV

AS

IVE

SE

RV

ICE

PLA

TFO

RM

WP2

Innovations

WP3 Innovations

WP4 Innovations

The Integration of WP innovations were completed through the selected ‘Nidaros’ Scenario.


Nidaros scenario

Describe nidaros scenario


Daidalos WP5 Task Forces

To evolve and implement this scenario, task forces were created

• Scene analysis Task Force (Input from all WP’s)

• Scene Step analysis Task Force (Input from WP5 step responsible)

• Mapping and Deployment Task Force

Maps WP1.1 scenes description considering real components developments and interactions

WP1.1 SELECTED SCENES ANALYSIS

IMPLEMENTATION GROUP ANALYSIS

SCENARIO DRIVEN DEMONSTRATION & TEST SITES DESIGN

WP5 Scenes Analysis Task Force

WP2...WP4 IMPLEMENTATION PLANS

WP2 ... WP4 INTERDEPENDENCIES

CHECKING

Implementation Group Interdependences checking Task Force

Missing interfaces and possible gaps are detected

REVIEWED WP2 ... WP4 IMPLEMENTATION PLANS

SCENES MAPPING

SCENES TECHNICAL DESCRIPTION

Whole Implementation Group involved - WP2 ... WP4 leaders, WP2 ... WP4 Activity leaders and WP5


Daidalos Integration Model

Due to the complexity of the Daidalos Architecture, the integration model addressed the following main areas

• Integrated Testbed(2 integrated test sites) 1. Sophia Antopolis,France 2. Aveiro, Portugal

• Integration-oriented developments– Intra work package integration activities– Formalisation of Integration roles and processes– Identification of best Integration and Testing strategy (i.e. sandwich testing)

• Conformance Test Specification– Identification of Nidaros specific WP interfaces– Definition of Scenario specific Conformance tests– Test Case Definition : Test Case Naming (e.g. N3:01), test summary, API’s &

interfaces involved, initial conditions – Test Report : Verdicts, person executed test, any closure actions and impacts,

comments and possible actions to be performed if test fails.


Daidalos Testbed

Daidalos Testbed

1. Daidalos Physical Testbed2. Visualisation activities3. Validation activities and conclusions


Daidalos Physical Deployment

Physical Deployment Nidaros

Switch

Core Router

nidaros_server_wp4nidaros_server_thirdparty 1

AR 2WLAN 2

TD-CDMA

nidaros_pda_bart nidaros_carpc_bart

AR 4DVB-T

MMSPP

nidaros_pda_bossnidaros_pda_rosa

Firewall

nidaros_server_streaming

ANQoSBr1ANQoSBr2

AR1 Wlan1

AR3 Wlan3

IPv6

IPv4

nidaros_homepc_bart

AR5

A4C QoS

RemoteAccess

ANQoSBPM ANQoSB

PM

MMSPB/P, MMG, maybe the MCS

CMSPBMNS

A4CAG

SDS

ARMNME

Newscast application,

MMSPUA, WP4 RS, QoSClient,

PaC, MTC

VideoTelephony application, MMSPUA,

QoSClient, PaC, MTC,..

WIFI/TD-CDMA/DVB-TNewscast and

VideoTelephony application, MMSPUA, QoSClient, PaC,

MTC,..

MMSPUA for messaging?

VideoTelephony application, MMSPUA,

QoSClient, PaC, MTC,…

ARM, Paa, NME, PA, QoSAL,

FHOAttendant,…


FHOAttendant,…


FHOAttendant,…


FHOAttendant,…


FHOAttendant,…

EM, PSM, PERS,SPM, CM, RM

AN1

CN

AN2

WLAN 1

WLAN 3


For European based conferences the daidalos testbed was setup in a mobile Science Truck which demonstrated Daidalos Innovations.

Daidalos Mobile Testbed


Daidalos Visualisation

Virtualisation Tool (DLR)

Figure 8 we have shown the layout for the CarPC view (a similar view was prepared for the PDA view) aftersome messages have been passed. It shows the simulated status of the network components and the messagesfrom the major WP4 subsystems and third party services. The colour of the arrows indicates the presence ofrecent message traffic over these connections.


Daidalos Visualisation

Lucent Virtualisation Tool


Daidalos Integration Testing

0

5

10

15

20

25

30

Step -1 Step 0 Step 1 Step 2 Step 3 Step 4 Step 5 Step 6

Planned TCAttempted TCSuccessful TCNo of Failures

Validation of the Nidaros Integrated Demonstrator conformance tests

• Sophia Antopolis in November 2005 , Aveiro in March 2006.

The 1st validation could only produce very high-level results (i.e. pass/fail of TC).

- Problems related to network layer, Mobile IP and WP2 network drivers which were unstable

As issues were resolved we were able to validate the demonstrator at a much lower level of detail.

Conformance session in Aveiro up to 120 test cases were planned, based on the Nidaros Test case specifications.


Integration Testing

Example Test Case

Bart is driving on the motorway, which triggers the launch of the Traffic information Service. Bart arrives at the airport, and continues to drive towards the car

parking area of the airport. His car system screen shows the airport information carrousel. Information about all

flights will be shown. Bart parks and leaves his car, taking his PDA with him.

A transfer is invoked on the transferring components in the old service and starts the new service on PDA and stops the old service on CarPC. The airport arrivals

information can now be seen on Barts PDA as he enters the airport arrival terminal.


Integration Issues Encountered

• Unstable MIPv6, switch from Mandrake to Ubuntu

• Machines crashing and rebooting became time consuming.

• Minor Errors encountered, led many times to major complications.

• Initial steps and configurations unforeseen eroded into valuable scheduled testing allocated time.


Conclusion and Results

• All tests performed on the test-bed successfully used Mobile IP, which remained very stable on Ubuntu in comparison to earlier attempts at using mobile IP on top of Mandrake.

• WP2 WLAN drivers were relatively stable compared to their earlier performance in Sophia.

• Route Optimisation worked over Mobile IP, with very noticeable performance improvements as compared to earlier tests on WP4 standalone test-beds.

• Registration module and several other components were dummy’s because of lack of integration on Ubuntu (previously worked under Mandrake).

• Communication was a main issue encountered during integration• Key point - developers to meet iteration delivery deadlines

• Scenario step planning contributed positively to the integration process.

• The 1st successful integrated testing utilising all Work packages took place at Aveiro.


End Of Presentation

Thank You For Your Time

Contact details : Frances Cleary Grant, Miguel Ponce de LeonOrganisation: TSSG , Waterford Institute Of Technology